What are the pros and cons of storing files directly in a SQL Server database?

One or our databases currently stores information related to documents that are stored in the filesystem but considering storing these documents in the database itself.

The primary advantage of storing files in your SQL Server database is that it avoids the problems that occur when files are changed in your filesystem (which can result in broken link references stored in your db or files that are out of sync with the information in your database). The disadvantages of storing files in your db include the potentially significant increase in db size that may occur depending on the number and nature of files you plan to store, and the potential negative impact on db performance related to accessing these files (the smaller the number and size of files you plan to store in the db, the less relevant these disadvantages become). While there are many options for optimizing performance of and managing large dbs, your organization's db management and backup tools or policies may make storing files in your db impractical. It is also important to consider the application you are using to access your db since designing the application to manage the process of file changes between your filesystem and db may produce the same advantage as storing the file in the db without the disadvantages. Lastly, the FILESTREAM feature in SQL Server offers a hybrid option designed to provide the benefits of storing files in the database while actually storing files in the filesystem.